feat: custom domain and slug commands (stacked on full-stack deploy) - #559

Note

Description

Adds two new command groups to the CLI for managing an app's public addressing: base44 domains (add/list/remove custom domains, backed by Cloudflare custom hostnames) and base44 slug (show/set/reset the app's *.base44.app subdomain). Both follow the existing core/cli split — Zod-validated snake_case→camelCase API layers under src/core/, thin presentation commands under src/cli/commands/ — and both fully support the global --json flag. Built on top of the full-stack Workers deploy work in the target branch, where a deployed app needs a stable public hostname.

Related Issue

None

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Other (please describe):

Changes Made

Custom domains (`base44 domains`)

• `src/core/domains/` — `addDomain`, `listDomains`, `removeDomain`, plus `waitForDomainActive` which polls the list endpoint (2s interval, 10min budget) until hostname + SSL are active
• Zod schemas transform the API's snake_case payloads to camelCase; Cloudflare-shaped DNS/ownership verification details pass through as `unknown` since they're opaque to the CLI
• `domains add ` prints the exact CNAME record to add, current status, and a warning when the app has no production deployment yet; `--wait` polls to active with a live-updating spinner message
• `domains list` renders a padded status table (or an empty-state message); `domains remove ` confirms interactively and requires `-y` in non-interactive mode

App slug (`base44 slug`)

• `src/core/slug/` — `getSlug` (reads the app document) and `updateSlug` (PATCH `metadata/slug`; `null` resets to auto-generated)
• When a slug is taken, the API's alternative suggestions are parsed off the error body and surfaced as a hint on the thrown `ApiError`
• `base44 slug` shows the current slug + derived URL, `slug set ` prints old → new plus URL, `slug reset` returns to the auto-generated slug

Supporting changes

• New `TimeoutError` (`UserError`, code `TIMEOUT`) for polled operations that exceed their budget
• Registered both command groups in `program.ts`
• Testkit: `TestAPIServer` now supports `PATCH` and gained domain/slug/app-document mocks with request capture
• `project/logs.ts`: moved the `--follow` + `--until`/`--order` mutual-exclusion checks to the top of the action so the flag conflict is reported before any network work

Testing

• I have tested these changes locally
• I have added/updated tests as needed
• All tests pass (`npm test`)

20 new integration tests across `tests/cli/domains.spec.ts` and `tests/cli/slug.spec.ts` covering human and `--json` output, the snake→camel transform, `--wait` polling to active, empty states, non-interactive `-y` enforcement, invalid slug format, taken-slug suggestions, and API error propagation.

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• I have updated `docs/` (AGENTS.md) if I made architectural changes

Additional Notes

No `docs/` updates are included. The new modules follow the existing resource/command patterns rather than introducing new architecture, but the two new command groups may be worth mentioning in `docs/commands.md` / `docs/deployments.md` alongside the full-stack deploy flow.

_{🤖 Generated by Claude | 2026-08-03 17:19 UTC | 78ee229}